Add default hashCode implementation to RetryConfiguration.AnnotationClassOrMethodPointcut #472
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request introduces a default implementation of
hashCode
forRetryConfiguration.AnnotationClassOrMethodPointcut
.I discovered that using Spring Cloud with configuration refreshing (specifically the
@RefreshScope
annotation andConfigServicePropertySourceLocator
as part of spring-cloud-config) can lead to a "java.lang.OutOfMemoryError: Metaspace". This occurs because theConfigServicePropertySourceLocator
is re-initialized with every refresh. Due to the absence of ahashCode
implementation, proxies for this class are regenerated each time, which causes them to be stored in theorg.springframework.cglib.core.internal.LoadingCache
(withRetryConfiguration.AnnotationClassOrMethodPointcut
being part of the composite key for this object).This results in an excessive accumulation of generated proxies in memory, ultimately leading to metaspace overflow.